Create partdb-release-script.sh#941
Closed
d-buchmann wants to merge 1 commit intoPart-DB:masterfrom
Closed
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #941 +/- ##
============================================
- Coverage 59.73% 59.71% -0.02%
Complexity 6036 6036
============================================
Files 529 529
Lines 20588 20588
============================================
- Hits 12298 12295 -3
- Misses 8290 8293 +3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Member
|
I would assume that this is obsolete with the merge of PR #1217 now |
Contributor
Author
|
Sure, the WebUI update manager looks really great. Closing. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I finally tested the update script and it worked =) (reference: #720)
Prerequisites:
The (guided) update process goes through ~4 stages:
0: check for new release
1: put current site into maintenance mode (requires an extra vhost to be set up...meh)
2: backup partdb database (only mysql at the moment...meh); git pull
3: Build according to the docs, transfer required files to testing location (yet another vhost...)
4: Transfer testing site to live enviroment, end maintenance mode
The process can be interrupted at any stage, by errors or by user interaction.
Resumption is possible through a stagefile.